home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
nt
/
ntkb.zip
/
NTKB.EXE
/
Q105
/
9
/
95.TXT
< prev
next >
Wrap
Text File
|
1993-11-22
|
3KB
|
91 lines
DOCUMENT:Q105995 19-NOV-1993 [W_NT]
TITLE :AT Command May Fail Copying Files to a LAN Manager Server
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
----------------------------------------------------------------------
SYMPTOMS
========
If you use the AT command to schedule a batch file that copies files
to a Microsoft LAN Manager server in a different Domain, the batch
file may fail and you will receive an "Access Denied" error message.
However, if you execute the batch file from a Command Prompt, it
successfully copies the files without generating an error message.
Example Batch File:
Net Use z: \\LMServer\Share
copy test.txt z:\
Net Use z: /d
CAUSE
=====
Without Domain information for the user account, using the AT command
does not succeed. This is because the account it is trying to validate
is the Administrator. The Schedule Service uses the Administrator's
rights for all access.
Without Domain information for the user account, using the AT command
does not succeed. This is because the account it is trying to validate
is the SYSTEM account. By default, the Schedule service uses the
SYSTEM account for access rights.
WORKAROUND
==========
There are two workarounds for this problem:
- Supply Domain information for the User in the "Net Use" command,
such as the following
Net Use z: \\LMServer\share password /USER:LMDomain\guest
where "guest" must be a valid account in the "LMDomain" Domain.
-or-
- Have the Schedule Service log on as a valid account on that
LAN Manager server by doing the following:
1. In the Control Panel window, choose the Services icon.
2. Select the Schedule Service, and then choose Startup.
3. Type the user account on the LAN Manager server (which matches a
local account) with sufficient rights and type the appropriate
password.
4. Restart the service so the changes take effect.
This option does not require changing the command line and will be
permanent unless it is changed.
Additional reference words: 3.10
KBCategory:
KBSubcategory: netsrv
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1993.